home *** CD-ROM | disk | FTP | other *** search
- C&C INI Editor (The Fan - s2lee@jupiter.scs.ryerson.ca)
- ------------------------------------------------------
-
- Usage: EDITINI {input}
- The saved output file is named TEXT.INI
- (input file is optional)
-
- This is an INI editor for Command & Conquer.
-
- This editor helps the user to create/edit the "AI" of a mission. If you are
- not familiar with the INI structure then you should read the documentation
- below to get some sort of idea of how the INI structure works.
-
- This editor is to provide some relief to the people who wish to create a good
- mission that involves reinforcements, triggers etc.
- ===============================================================================
-
- Things that this editor can do
- ------------------------------
- Create entries for following
- [Teamtypes]
- [Waypoints]
- [Triggers]
- [CellTriggers]
-
- The [Teamtypes] section is the designation of teams to be created, reinforced
- etc. depending on the [Triggers] section (where you select the type of units
- and the actions to execute).
-
- ■ Example of a Teamtypes entry would be:
-
- ■ attack1=Goodguy,x,x,x,x,x,x,x,x,TRAN:1,MCV:1,MTNK:3,UNLOAD:waypoint
- (where x is not important - i calculate them all for you)
- This means a Chinook would carry an MCV and 3 medium tanks and unload
- them at a Waypoint that you choose.
- -------------------------------------------------------------------------------
- The [Waypoints] section is the actual location on a 64 x 64 matrix map.
- (It is actually 62 x 62 because the of the "border" but nevertheless the cell
- location would be from 65 - 4030.
-
- ■ Example of a waypoint entry would be:
-
- ■ 10=2909 means Waypoint #10 is referring to the cell location 2909 in the map.
- -------------------------------------------------------------------------------
- The [Triggers] section would be responsible for creating units or executing an
- action from the [Teamtypes] section.
-
- ■ Example of a Trigger entry would be:
-
- ■ trig1=Time,Reinforce.,10,Goodguy,attack1
- "trig1" would execute once after 10 time units (time units may differ depending
- on the performance of your computer) have counted - and would bring in the
- "attack1" teamtype as a reinforcement to the GDI side.
- -------------------------------------------------------------------------------
- The [CellTriggers] section is described as
- "When a unit steps on cell location xxxx activate the Trigger blahblah."
-
- ■ Example of a Celltrigger entry would be:
-
- ■ 3021=trig1
- When a unit steps on cell location 3021, the trigger "trig1" would execute as
- explained in the trigger example above - In 10 units of time, GDI would receive
- reinforcements of 3 med. tanks and a MCV.
- ===============================================================================
- If you still don't know what's going on, just get an idea of the function
- of each section and then perhaps my program may help you understand the INI
- structure.
-
- Good Luck!
-
- Future considerations:
-
- * More efficient stack system
- * Ability to handle [BASES] and [Structures] so that you can select
- what the CPU can rebuild
- * Graphical interface (no time for it yet)
-
- Please email me for any suggestions.
-
- History & Revisions
- -------------------
- EDITINI v0.99
- - Initial bug test release
-
- EDITINI v1.00
- - Now displays in 43/50 column mode
- - Fixed some cosmetic displays (ie. Waypoint listings)
- - Fixed the [Teamtypes] vehicle selection to its proper listing
- - Updated the [Trigger] events with all the selections (ie Dropzones etc)
- - Hopefully this will hold out as a release
-
- EDITINI v1.0a
- - Corrected problem with random waypoint values when editing the
- teamtypes (when you have an existing waypoint it changed the number)
-
- EDITINI v1.0b
- - Fixed problem with deleting [triggers] and [teamtypes]
- - Added warning "Quit without saving new changes"
- - Better documentation
- - I think it is pretty much bug free??
-
- * Crud, there seems to be more revisions to correct bugs than new features!
-
- Many thanx go to Wayne M. McGee who probably spent more time debugging
- this program than I did. And Andrew Griffin (Buggy) for supplying info
- of the INI structure.
-
- Please report any bugs to
-
- The Fan
- (Simon)
- s2lee@jupiter.scs.ryerson.ca
-
- You may distribute freely without modifications to the program(s) / docs.
-